Information processing apparatus, method for controlling the same, and storage medium therefor

ABSTRACT

In an information processing apparatus connected to an external apparatus, when information indicating a change in a folder indicates that a new file has been appended to the folder, a document management application updates a screen so that existing files are arranged in order according to a specified sorting method and a new file is appended to a position, not according to the specified sorting method, at which the new file can be easily recognized.

BACKGROUND

Field of the Disclosure

Aspects of the present invention generally relate to an informationprocessing apparatus for controlling display processing in a documentmanagement application, a method for controlling the informationprocessing apparatus, and a storage medium therefor.

Description of the Related Art

When a plurality of information processing apparatuses is referring to afolder of a file server, the result of an operation for appending,editing, or deleting a file in the folder performed by a certaininformation processing apparatus may not be reflected on screens ofother information processing apparatuses. For example, when a user keepsmonitoring one folder, the user may be unable to notice a status changein the above-described folder.

As a technique for resolving this problem, Japanese Patent ApplicationLaid-Open No. 2012-43119 discusses a technique for monitoring aspecified folder, and, when a file is appended to the folder currentlybeing monitored, notifying a user of the appended file by using a pop-upmessage.

With the conventional technique, however, when the user is performing anoperation while monitoring a certain folder, for example, the user maybe unable to notice the pop-up message depending on the display positionof the pop-up message.

SUMMARY

Aspects of the present invention relate to enabling a user to easilyrecognize a change in a monitoring target folder.

According to an aspect of the present invention, an informationprocessing apparatus connectable to an external apparatus includes adisplay unit configured to display a screen in which existing files in afolder of the external apparatus are arranged in order according to aspecified sorting method, a receiving unit configured to receiveinformation indicating a change in the folder from the externalapparatus, and an updating unit configured to update display content ofthe screen according to the information received by the receiving unit.When the information indicating a change in the folder indicates that anew file has been appended to the folder, the updating unit updates thescreen so that the existing files are arranged in order according to thespecified sorting method and the new file is appended to a position atwhich the new file can be easily recognized by a user in order notaccording to the sorting method.

Further features of the present disclosure will become apparent from thefollowing detailed description of exemplary embodiments with referenceto the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an overall configuration of exemplary embodiments.

FIG. 2 is a block diagram illustrating a hardware configuration of aninformation processing apparatus.

FIG. 3 illustrates an example of a software configuration of a documentmanagement application.

FIG. 4 illustrates an example of a software configuration of a fileserver.

FIG. 5 illustrates an example of a user interface (UI) of the documentmanagement application.

FIG. 6 is a flowchart illustrating processing for updating a file list.

FIG. 7 illustrates an example of a correspondence table of an eventclass, the presence or absence of the file list, and a display updatingmethod.

FIG. 8 is a flowchart illustrating processing for updating the file listthrough OnCreated and OnChanged events.

FIG. 9 is a flowchart illustrating processing for updating the file listthrough an OnDeleted event.

FIGS. 10A and 10B are flowcharts illustrating processing for updatingthe file list through an OnRenamed event.

FIG. 11 is a flowchart illustrating processing for determining a fileserver type.

FIG. 12 is a flowchart illustrating processing for updating the filelist.

FIG. 13 is a flowchart illustrating details of event class changeprocessing.

FIG. 14 is a flowchart illustrating processing for updating the filelist according to an event.

FIG. 15 is a flowchart illustrating details of event wait processing.

FIG. 16 illustrates an example of a UI of the document managementapplication.

FIG. 17 illustrates an example of a UI of the document managementapplication.

FIG. 18 illustrates an example of a UI of the document managementapplication.

FIGS. 19A and 19B illustrate examples of UIs of the document managementapplication.

FIG. 20 illustrates an example of a UI of the document managementapplication.

DESCRIPTION OF THE EMBODIMENTS

Various exemplary embodiments, features, and aspects of the inventionwill be described in detail below with reference to the drawings.

FIG. 1 illustrates an overall configuration of preferable exemplaryembodiments of the present invention. Referring to FIG. 1, informationprocessing apparatuses 0101 are connected to a file server 0103 via anetwork 0102 capable of command communication.

FIG. 2 is a block diagram illustrating a hardware configuration of aninformation processing apparatus 0101 and the file server 0103illustrated in FIG. 1. The file server 0103 is an external apparatusconnectable to the information processing apparatuses 0101, and may alsobe a personal computer (PC).

A central processing unit (CPU) 0201 is a control unit of theinformation processing apparatus 0101. The CPU 0201 executes anapplication program, an operating system (OS), and a document managementapplication according to embodiments of the present invention stored ina hard disk drive (HDD) 0207. The CPU 0201 also performs control totemporarily store in a random access memory (RAM) 0206 information andfiles necessary for program execution.

A read-only memory (ROM) 0202 is a storage device for storing programs,such as basic I/O programs, font data used for file processing, andother various data such as template data.

A network interface card (NIC) 0203 serves as an interface to thenetwork 0102. The information processing apparatus 0101 exchanges datawith an external apparatus via the NIC 0203.

A keyboard 0204 is an input device which functions as an instructioninput device. A user uses the keyboard 0204 to input a control commandto a drawing program according to embodiments of the present inventionor a text.

The RAM 0206 is a temporary storage device which functions as a mainmemory and a working area for the CPU 0201.

The HDD 0207, one of external storage units, functions as a mass storagedevice for storing the application program, the OS, and relatedprograms.

A display 0208 is an output device which functions as a display unit fordisplaying a command input from the keyboard 0204 or the status of thedocument management application according to embodiments of the presentinvention.

A system bus 0209 connects between components in the informationprocessing apparatus 0101 and the file server 0103, and manages dataflow in the information processing apparatus 0101 and the file server0103.

FIG. 3 illustrates a software configuration of the document managementapplication for embodying the present invention.

A document management application 0300 is a program module operating onthe information processing apparatus 0101. The document managementapplication 0300 is loaded into the RAM 0206 and then executed by theCPU 0201.

A library management unit 0301 manages the location of a file serverwhich can be referred to by the document management application 0300.The document management application 0300 performs file operationsreferring to the file server managed by the library management unit0301.

A display unit 0302 receives an input from the keyboard 0204, anddisplays on the display 0208 the result of processing by the documentmanagement application 0300.

A file operation unit 0303 performs file operations. Specifically, thefile operation unit 0303 performs operations for moving, copying, anddeleting files in the file server 0103 in response to inputs from thekeyboard 0204.

A file list acquisition unit 0304 acquires a file list in a foldercurrently being referred to out of files stored in the file server 0103.

A file list updating unit 0305 updates the display information of a filelist screen displayed on the display unit 0302 based on the currentlydisplayed file list and file information (file list) acquired by thefile list acquisition unit 0304. Alternatively, the file list updatingunit 0305 updates the display information of the file list screendisplayed on the display unit 0302 based on file information of an eventreceived from an event receiving unit 0307.

An event monitoring specification unit 0306 requests the file server0103 to monitor a change in a file at the position currently beingdisplayed on the display unit 0302. When a file in a monitoring targetfolder specified by the event monitoring specification unit 0306 ischanged, the file server 0103 transmits a relevant event to the eventreceiving unit 0307. Then, the event receiving unit 0307 receives theevent.

Upon reception of the event, the event receiving unit 0307 notifies thefile list updating unit 0305 of what has occurred in which file.

FIG. 4 illustrates a system configuration of the file server 0103 forembodying the present invention.

A file storage unit 0401 is an area for storing files. Files can bestored in the file storage unit 0401 not only from the documentmanagement application 0300 but also from various applications.

A file monitoring unit 0402 monitors a change in a specified folder inthe file storage unit 0401 specified by the event monitoringspecification unit 0306 of the document management application 0300.

When a file in the specified folder is changed, an event notificationunit 0403 notifies the event receiving unit 0307 of information aboutthe changed file.

Specifically, the event notification unit 0403 notifies the eventreceiving unit 0307 of an “OnCreated” event indicating that a new filehas been generated, and an “OnChanged” event indicating that an existingfile has been changed. The event notification unit 0403 also notifiesthe event receiving unit 0307 of an “OnDeleted” event indicating that anexisting file has been deleted, and an “OnRenamed” event indicating thatan existing file has been renamed.

When the “OnCreated”, “OnChanged”, or “OnDeleted” event is notified, theevent notification unit 0403 also notifies the event receiving unit 0307of the file name of a file which has been changed. When the “OnRenamed”event is notified, the event notification unit 0403 notifies the eventreceiving unit 0307 of both the file name of the original file and thefile name of the new file.

FIG. 5 illustrates an example of a UI of the document managementapplication 0300. A menu 0501 displays a list of file operation commandsto allow the user to execute these commands.

An address bar 0502 displays a path of a folder currently being referredto. When the user directly inputs a folder path in the address bar 0502,files existing in the folder on the specified path are displayed in listform in a file list view 0505. In the present specification, filesexisting in the monitoring target folder when the user selects themonitoring target folder are referred to as existing files, and a newfile appended therein is referred to as a new file. When it is notnecessary to clearly distinguish between an existing file and a newfile, these are simply referred to as a file.

When the user inputs a search keyword in a simple search bar 0508, alist of files containing the search keyword are displayed in the filelist view 0505.

A tool bar 0503 displays shortcut buttons corresponding to executableoperations in the menu 0501. The display in the file list view 0505 isalso changed by using the buttons in the tool bar 0503. In the presentexemplary embodiment, the display form of the file list view 0505 can beswitched between a thumbnail form and a list form.

A navigation pane 0504 displays a list of registered libraries, andindicates the position of a folder currently being referred to. Therelation between a library and folders is such that the library is at ahigher hierarchical level and folders exist at subordinate hierarchicallevels of the library. Further, a setting applied to a library is alsoapplied to folders under the library.

The file list view 0505 displays in list form folders and files includedin the folder path displayed in the address bar 0502.

Specifying a display form in the tool bar 0503 changes the display formof the file list view 0505. The example in FIG. 5 illustrates thethumbnail display form.

A preview pane 0506 previews the contents of a file selected in the filelist view 0505. The preview pane 0506 can display the contents of aplurality of pages by specifying the next page.

An output bar 0507 includes buttons assigned respective actions. Whenthe user presses a button in the output bar 0507, the action associatedwith the button is applied to the file selected in the file list view0505. In the present exemplary embodiment, actions of printing,attachment to mail, and movement to folder (respectively referred to asprinting action, attachment-to-mail action, and movement-to-folderaction) can be registered in the output bar 0507.

When the user presses the printing action, the document managementapplication 0300 prints the file selected when the printing action ispressed. When the user presses the attachment-to-mail action, thedocument management application 0300 attaches the file selected when theattachment-to-mail action is pressed to a new mail of a mail clientassociated with the OS.

When the user presses the movement-to-folder action, the documentmanagement application 0300 moves to the registered folder path the fileselected when the movement-to-folder action is pressed.

The following describes a method for immediately reflecting a change inthe monitoring target folder to the file list view 0505 performed by thedocument management application 0300 according to the present exemplaryembodiment, with reference to the flowchart illustrated in FIG. 6. Eachstep of flowcharts according to the present specification is implementedwhen a program relevant to each flowchart is loaded into the RAM 0206and then executed by the CPU 0201.

In step S0601, the document management application 0300 opens anarbitrary folder selected by the user from a file server registered as alibrary.

In step S0602, the document management application 0300 acquires a filelist of the opened folder, and displays in the file list view 0505 theacquired list of existing files.

In step S0603, the document management application 0300 monitors theopened folder as a monitoring target folder. When any file in themonitoring target folder has been changed, the file server 0103 notifiesthe document management application 0300 of information about the changein the folder. In the present specification, information about a changein a file is referred to as an event.

In step S0604, the document management application 0300 receives anevent notified from the file server 0103.

Upon reception of the “OnCreated” event, then in step S0605, thedocument management application 0300 performs append, rename, or deleteprocessing for the OnCreated event.

Upon reception of the “OnChanged” event, then in step S0606, thedocument management application 0300 performs append, rename, or deleteprocessing for the OnChanged event.

Upon reception of the “OnDeleted” event, then in step S0607, thedocument management application 0300 performs append, rename, or deleteprocessing for the OnDeleted event.

Upon reception of the “OnRenamed” event, then in step S0608, thedocument management application 0300 performs append, rename, or deleteprocessing for the OnRenamed event.

FIG. 7 illustrates a list for defining operations for changing a filelist updating method depending on the received event, whether a filenotified by the event exists in the acquired file list, and whether,when an entity of the file notified by the event is acquired, theexistence of the entity can be confirmed. The file list illustrated inFIG. 7 indicates operations in steps S0605, S0606, S0607, and S0608 ofthe flowchart illustrated in FIG. 6.

FIG. 8 is a detailed flowchart illustrating steps S0605 and S0606performed upon reception of the “OnCreated” event and the “OnChanged”event, respectively.

In step S0801, the document management application 0300 acquires a filename received in the relevant event.

In step S0802, the document management application 0300 determineswhether a file having the same file name as the one acquired in stepS0801 exists in the file list acquired from the monitoring targetfolder.

When the file name included in the relevant event exists in the filelist acquired from the monitoring target folder (YES in step S0802),then in step S0803, the document management application 0300 determineswhether the file received in the relevant event actually exists.Specifically, in step S0803, the document management application 0300determines whether the file received in the relevant event exists in themonitoring target folder.

When the file name received in the relevant event exists in the filelist acquired from the monitoring target folder (YES in step S0802), andactually exists in the monitoring target folder (YES in step S0803), thedocument management application 0300 determines that the relevant filehas been updated. Then in step S0804, the document managementapplication 0300 updates the file at the current display position in thefile list.

When the file name received in the relevant event exists in the filelist acquired from the monitoring target folder (YES in step S0802), anddoes not actually exist in the monitoring target folder (NO in stepS0803), the document management application 0300 determines that therelevant file has been deleted. Then in step S0805, the documentmanagement application 0300 deletes the file from the file list.

When the file name received in the relevant event does not exist in thefile list acquired from the monitoring target folder (NO in step S0802),then in step S0806, the document management application 0300 determineswhether the file received in the relevant event actually exists in themonitoring target folder, similar to step S0803.

When the file name received in the relevant event does not exist in thefile list acquired from the monitoring target folder (NO in step S0802),and actually exists in the monitoring target folder (YES in step S0806),the document management application 0300 determines that a new file hasbeen appended. Then in step S0807, the document management application0300 appends the new file to the end of the file list, not depending ona file display condition and a sort condition. The present exemplaryembodiment is described to append a new file to the end of the file listat which the new file can be easily recognized by the user. However, theposition at which a new file is appended is not limited thereto, and maybe any position at which the new file can be easily recognized by theuser. For example, a new file may be appended to the top of the filelist.

When the file name received in the relevant event does not exist in thefile list acquired from the monitoring target folder (NO in step S0802),and does not actually exist in the monitoring target folder (NO in stepS0806), the document management application 0300 determines that thefolder remains unchanged. Then in step S0808, the document managementapplication 0300 performs no operation.

FIG. 9 is a detailed flowchart illustrating step S0607 performed uponreception of the “OnDeleted” event.

In step S0901, the document management application 0300 acquires a filename received in the relevant event.

In step S0902, the document management application 0300 determineswhether a file having the same file name as the one received in therelevant event exists in the file list acquired from the monitoringtarget folder.

When a file having the same file name as the one received in therelevant event exists in the file list acquired from the monitoringtarget folder (YES in step S0902), then in step S0903, the documentmanagement application 0300 determines whether the file received in therelevant event actually exists in the monitoring target folder.

When a file having the same file name as the one received in therelevant event exists in the file list acquired from the monitoringtarget folder (YES in step S0902), and actually exists in the monitoringtarget folder (YES in step S0903), the document management application0300 determines that the relevant file has been updated. Then in stepS0904, the document management application 0300 updates the file at thecurrent display position in the file list, similar to step S0804.

When a file having the same file name as the one received in therelevant event exists in the file list acquired from the monitoringtarget folder (YES in step S0902), and does not actually exist in themonitoring target folder (NO in step S0903), the document managementapplication 0300 determines that the relevant file has been deleted.Then in step S0905, the document management application 0300 deletes thefile from the file list, similar to step S0805.

When a file having the same file name as the one received in therelevant event does not exist in the file list acquired from themonitoring target folder (NO in step S0902), the document managementapplication 0300 determines that the folder remains unchanged. Then instep S0906, the document management application 0300 performs nooperation, similar to step S0808.

FIGS. 10A and 10B are detailed flowcharts illustrating step S0608performed upon reception of the “OnRenamed” event.

In step S1001, the document management application 0300 acquires anoriginal file name received in the relevant event and a file name afterrenaming.

In step S1002, the document management application 0300 determineswhether an original file having the same file name as the one receivedin the relevant event exists in the file list for the monitoring targetfolder. When an original file name exists in the file list for themonitoring target folder (YES in step S1002), then in step S1003, thedocument management application 0300 stores A=True. Otherwise, when anoriginal file name does not exist in the file list (NO in step S1002),then in step S1004, the document management application 0300 storesA=False.

In step S1005, the document management application 0300 determineswhether the original file received in the relevant event actually existsin the monitoring target folder. When the original file received in therelevant event actually exists in the monitoring target folder (YES instep S1005), then in step S1006, the document management application0300 stores B=True. Otherwise, when the original file received in therelevant event does not actually exist in the monitoring target folder(NO in step S1005), then in step S1007, the document managementapplication 0300 stores B=False.

In step S1008, the document management application 0300 determineswhether the file having the file name after renaming received in therelevant event exists in the file list for the monitoring target folder.When the file having the file name after renaming received in therelevant event exists in the file list for the monitoring target folder(YES in step S1008), then in step S1009, the document managementapplication 0300 stores C=True. Otherwise, when the file having the filename after renaming received in the relevant event does not exist in thefile list (NO in step S1008), then in step S1010, the documentmanagement application 0300 stores C=False. In step S1011, the documentmanagement application 0300 determines whether the file having the filename after renaming received in the relevant event actually exists inthe monitoring target folder.

When the file having the file name after renaming received in therelevant event actually exists in the monitoring target folder (YES instep S1011), then in step S1012, the document management application0300 stores D=True. Otherwise, when the file having the file name afterrenaming received in the relevant event does not actually exist in themonitoring target folder (NO in step S1011), then in step S1013, thedocument management application 0300 stores D=False.

In step S1014, the document management application 0300 refers to thevalues A, B, C, and D to change the method for appending the relevantfile to the file list depending on combinations of the values A, B, C,and D. When A to D are all True, when A=True, B=True, C=False, andD=True, or when A=True, B=True, C=False, and D=False, then in stepS1015, the document management application 0300 updates the file havingthe file name after renaming, and the changed file name is displayed atthe same position in the file list.

When A=True, B=True, C=True, and D=False, then in step S1016, thedocument management application 0300 updates the file having the filename after renaming, displays the file name at the same position in thefile list, and deletes the file name before renaming from the file list.

When A=True, B=False, C=True, and D=True, when A=True, B=False, C=False,and D=True, or when A=True, B=False, C=False, and D=False, then in stepS1017, the document management application 0300 deletes the file havingthe file name after renaming from the file list.

When A=False, B=True, C=True, and D=True, or when A=False, B=True,C=True, and D=False, then in step S1018, the document managementapplication 0300 updates the original file name before renaming to thefile name after renaming, and does not move the relevant file positionin the file list.

When A=True, B=False, C=True, and D=False, then in step S1019, thedocument management application 0300 deletes the file having the filename after renaming from the file list, and also deletes the file havingthe original file name before renaming.

When A=False, B=True, C=False, and D=True, or when A=False, B=True,C=False, and D=False, then in step S1020, the document managementapplication 0300 appends the file having the file name after renaming tothe end of the file list.

When A=False, B=False, C=True, and D=False, then in step S1021, thedocument management application 0300 deletes the file having theoriginal file name before renaming from the file list.

When A=False, B=False, C=True, and D=True, when A=False, B=False,C=False, and D=True, or when A=False, B=False, C=False, and D=False,then in step S1022, the document management applications 0300 performsno operation assuming that files remain unchanged.

As described above, a new file is appended to the end of the file list,and an updated file is updated at the same position.

The following describe screens obtained by embodying the presentexemplary embodiment.

FIG. 5 illustrates an example of a UI of the document managementapplication 0300 displaying a list of existing files stored in thefolder specified in the address bar 0502. The file list has been sortedby file name.

When a new file is appended in the folder specified in the address bar0502, the document management application 0300 receives the relevantevent from the file server 0103, and updates the screen illustrated inFIG. 5 to the screen (file list) illustrated in FIG. 18. If the filename of a new file 1801 is Add.pdf, the new file will be appendedbetween A.pdf and B.pdf in the file list view 0505 when complying thesorting rule.

However, according to the present exemplary embodiment, the new fileappended in the monitoring target folder is appended to the end of thefile list, as with the file 1801. Thus, while the user is referring tofiles sequentially from the top downward in sorted order, the new fileis not inserted between files as a result of sorting, but is appended tothe end of the file list. This allows the user to easily notice theappended new file.

The screen may be updated so that the new file is displayed at the lowerend, at the upper end, or at the top of the file list, other than at theend of the file list. Also when existing files are displayed in the filelist view 0505 in a state where the existing files are sorted by datatype or data size, the document management application 0300 performsprocessing according to the present exemplary embodiment, allowing theuser to easily recognize a change in the monitoring target folder.

Although, in the first exemplary embodiment, the document managementapplication 0300 updates the file list upon reception of an event, somefile servers are not capable of event transmission. In a secondexemplary embodiment, the document management application 0300determines whether the file server is capable of event transmission. Thefollowing describes a method for appending a new file through periodicalmonitoring when the document management application 0300 determines thatthe file server is not capable of event transmission. In thedescriptions of the second exemplary embodiment, points duplicated withthe first exemplary embodiment will be omitted.

In library registration processing, the document management application0300 specifies a registration class to the library management unit 0301.When the registration class is “DIRECTLY REFERABLE”, a reference targetfile server is able to edit files thereon. When the registration classis “NOT DIRECTLY REFERABLE”, the reference target file server is unableto edit files thereon.

A Server Message Block (SMB) server is an example of a file serverhaving a registration class of “DIRECTLY REFERABLE”. A Web-basedDistributed Authoring and Versioning (WebDAV) server is an example afile server having a registration class of “NOT DIRECTLY REFERABLE”.

When the user registers as a library a file server in the librarymanagement unit 0301 of the document management application 0300, theuser specifies whether the registration class is “DIRECTLY REFERABLE”.FIGS. 19A and 19B illustrate examples of UIs displayed in the libraryregistration processing.

FIG. 19A illustrates an example of a library selection screen. When theuser executes a command for displaying the screen illustrated in FIG.19A with the menu 0501, the screen illustrated in FIG. 19A appears. Alibrary type selection list 1902 in a library selection screen 1901displays a list of registerable libraries. Types of registerablelibraries are defined by the document management application 0300.

When the user selects a library type and then selects an OK button 1903,a library registration screen appears.

FIG. 19B illustrates an example of a network library registrationscreen. A network library registration screen 1904 is displayed when theuser selects NETWORK LIBRARY in the library type selection list 1902.

The user specifies a path of the folder to be registered in a folderpath specification text box in the screen illustrated in FIG. 19B. Whenthe user specifies a library name for the registration target folder andthen presses an OK button 1906, the library is registered in thedocument management application 0300, and displayed in the navigationpane 0504.

FIG. 11 is a detailed flowchart illustrating processing for determiningwhether, after the library is registered as described above, thedocument management application 0300 updates the file list through anevent or through periodical monitoring.

In step S1101, the document management application 0300 selects auser-selected library from the registered libraries.

In step S1102, the document management application 0300 determineslibrary information (registration class) registered in the selectedlibrary.

When the library information indicates that a directly referable library(DIRECTLY REFERABLE in step S1102), then in step S1103, the documentmanagement application 0300 acquires file server information from thepath of the registered library information.

In step S1104, the document management application 0300 determineswhether the file server employs the New Technology (NT) File System.

When the server employs the NT File System (YES in step S1104), thedocument management application 0300 determines that the file server iscapable of event transmission, then in step S1105, the documentmanagement application 0300 monitors an event from the file server.

Otherwise, when the registration information registered in the selectedlibrary is “NOT DIRECTLY REFERABLE” (NOT DIRECTLY REFERABLE in stepS1102), or when the file server information acquired in step S1103 isnot the NT File System (NO in step S1104), the document managementapplication 0300 determines that the file server corresponding to theselected library cannot be monitored with regard to events.

Then in step S1106, the document management application 0300periodically monitors the file server. When periodically monitoring thefile server, the document management application 0300 acquires a filelist for the target folder at predetermined fixed intervals, andcompares the file list currently displayed on the document managementapplication 0300 with the acquired file list. As a result of thecomparison, the document management application 0300 appends to the enda file which exists only in the acquired file list, and deletes from theacquired file list a file which does not exist in the currentlydisplayed file list.

Thus, the document management application 0300 is able to switch betweenevent monitoring and periodical monitoring.

Although, in first exemplary embodiment, the document managementapplication 0300 updates the file list upon reception of an event, somespecific applications perform a unique operation depending on a fileoperation. For example, when overwriting is instructed, a specificapplication performs the following processing instead of directlyupdating the file. In the descriptions of a third exemplary embodiment,points duplicated with the first and the second exemplary embodimentswill be omitted.

When overwriting is instructed, the specific application generates a newfile having an extension of .tmp as a different file from the originalfile subjected to overwriting. At the timing of this generationprocessing, the file server issues the OnCreated event to the documentmanagement application 0300. With the new file having an extension of.tmp generated when overwriting is specified, the extension .tmp ishighly likely to have a hidden file attribute, the extension is highlylikely to be .tmp, and the file name is highly likely to be“$Recycler.DT,˜$”.

Then, the specific application changes the extension of the originalfile subjected to overwriting to .tmp. At the timing of the file namechange processing, the file server issues the OnRenamed event to thedocument management application 0300.

Then, the specific application changes to the original file name thefile name of the file having an extension of .tmp generated as adifferent file from the original file and stores such file, thusachieving overwriting and storing. Since the file name has been changedin the storage processing, the file server issues the OnRenamed event tothe document management application 0300.

Subsequently, at the timing of the delete processing for deleting therenamed file having an extension of .tmp, the file server issues theOnDeleted event to the document management application 0300.

The third exemplary embodiment will describe a method in which, even ifsuch a specific application exists, the document management application0300 appends a new file to the end, similar to the first exemplaryembodiment, and updates the updated file at the same position.

FIG. 12 is a flowchart illustrating processing in which the documentmanagement application 0300 updates the file list according to areceived event. In the descriptions of FIG. 12, elements duplicated withthose in FIG. 6 will be omitted.

When the document management application 0300 receives an event (YES instep S0604), then in step S1201, the document management application0300 performs event class change processing. The document managementapplication 0300 changes the received event class as required throughthe event class change processing, and performs steps S0605, S0606,S0607, and S0608 based on the changed event.

FIG. 13 is a detailed flowchart illustrating the event class changeprocessing in step S1201. Basically, processing illustrated in FIG. 13is performed by the event receiving unit 0307 of the document managementapplication 0300.

In step S1301, the event receiving unit 0307 receives an event. In stepS1302, the event receiving unit 0307 determines an event class of thereceived event.

When the event class of the received event is determined to be OnCreatedor OnChanged (OnCreated/OnChanged in step S1302), then in step S1303,the event receiving unit 0307 acquires a file attribute received in therelevant event.

In step S1304, the event receiving unit 0307 determines whether theacquired attribute is a hidden attribute.

When the acquired attribute is determined to be a hidden attribute, orwhen the attribute cannot be acquired since the file itself does notexist in the monitoring target folder of the file server (YES orATTRIBUTE ACQUISITION NOT POSSIBLE in step S1304), then in step S1310,the event receiving unit 0307 does not notify the file list updatingunit 0305 of the relevant event. Specifically, when the OnCreated eventis received and the file corresponding to the relevant event has ahidden attribute, the received event is highly likely to be an event fora file generated as another file for overwriting described above.

It is not necessary to update the file list view 0505 by using a filecorresponding to such an event. Therefore, the event receiving unit 0307does not notify the file list updating unit 0305 of the relevant event.When the event receiving unit 0307 does not notify the event in stepS1310, the event receiving unit 0307 deletes the received event.

When the attribute acquired in step S1304 is determined not to be ahidden attribute (NO in step S1304), then in step S1305, the eventreceiving unit 0307 determines whether the file corresponding to theevent received in step S0604 has a specific extension. Although, in thepresent exemplary embodiment, the event receiving unit 0307 determineswhether the extension is .tmp, .iwx, .iwn, .iwu, or .db, the extensionis not limited thereto.

The processing in step S1305 is achieved when the document managementapplication 0300 refers to the extension of the file corresponding tothe relevant event in a folder of a monitoring target file server.

The file generated as another file for overwriting does not necessarilyhave a hidden attribute. Therefore, for example, even if the filegenerated as another file for overwriting does not have a hiddenattribute, the event receiving unit 0307 is able to suitably determinewhether it should notify the file list updating unit 0305 of therelevant event, by performing the processing in step S1305.

When the extension of the file corresponding to the relevant event isdetermined to be a specific extension (YES in step S1305), then in stepS1310, the event receiving unit 0307 does not notify the file listupdating unit 0305 of the relevant event.

When the extension of the file corresponding to the relevant event isdetermined not to be a specific extension (NO in step S1305), then instep S1306, the event receiving unit 0307 determines whether the filename of the file corresponding to the relevant event starts with aspecific name. Although, in the present exemplary embodiment, the eventreceiving unit 0307 determines whether the file name of the filecorresponding to the relevant event starts with “$Recycler.DT,˜$”, thespecific name is not limited thereto.

The file generated as another file for overwriting does not necessarilyhave a hidden attribute and have the above-described extended specificextension. Therefore, for example, also when the file generated asanother file for overwriting does not have a hidden attribute, and theextension of the file generated for overwriting is not a specificextension, the event receiving unit 0307 is able to suitably determinewhether it should notify the file list updating unit 0305 of therelevant event.

When the file name of the file corresponding to the relevant event isdetermined to start with the specific name (YES in step S1306), then instep S1310, the event receiving unit 0307 does not notify the file listupdating unit 0305 of the relevant event.

When the file name of the file corresponding to the relevant event isdetermined not to start with the specific name (NO in step S1306), thenin step S1307, the event receiving unit 0307 determines whether an eventchange flag is provided.

When the event change flag is determined not to be provided (NO in stepS1307), then in step S1309, the event receiving unit 0307 notifies thefile list updating unit 0305 of the relevant event as it is.

Otherwise, when the event change flag is determined to be provided (YESin step S1307), then in step S1308, the event receiving unit 0307changes the OnRenamed event to the OnChanged event. Then in step S1309,the event receiving unit 0307 notifies the file list updating unit 0305of the relevant event.

When the received event is the OnDeleted event (OnDeleted in stepS1302), the event receiving unit 0307 advances the processing to stepS1305.

When the received event is the OnRenamed event (OnRenamed in stepS1302), then in step S1311, the event receiving unit 0307 determineswhether the extension before renaming is .tmp. When the eventnotification unit 0403 notifies the event receiving unit 0307 of theOnRenamed event, it notifies the event receiving unit 0307 of both thefile name of the original file and the file name of the new file.Therefore, the event receiving unit 0307 is able to achieve theprocessing in step S1311 by referring to the file name of the originalfile.

When the extension before renaming is determined to be .tmp (YES in stepS1311), then in step S1312, the event receiving unit 0307 prepares anevent change flag. In step S1314, the event receiving unit 0307 uses thefile name after renaming for subsequent determinations. Then, theprocessing proceeds to step S1303.

When the extension before renaming is determined not to be .tmp (NO instep S1311), then in step S1313, the event receiving unit 0307determines whether the extension after renaming is .tmp. The eventreceiving unit 0307 is able to achieve the processing in step S1313 byreferring to the file name of the new file notified in the OnRenamedevent by the event notification unit 0403.

When the extension after renaming is determined to be .tmp (YES in stepS1313), then in step S1310, the event receiving unit 0307 does notnotify the file list updating unit 0305 of the relevant event.Otherwise, when the extension is determined not to be .tmp (NO in stepS1313), the event receiving unit 0307 advances the processing to stepS1314.

Thus, by changing the event class in this way, the document managementapplication 0300 is able to perform an overwriting operation as expectedat the time of overwriting even if overwriting processing due to anapplication-specific operation is executed. Specifically, the positionof the overwritten file remains unchanged in the file list view 0505.

Referring to FIG. 13, the execution order of the determinationprocessing insteps S1304 to S1306 is not limited thereto. For example,steps S1305, S1304, and S1306 may be executed in this order. Further, itis not necessary to execute all of the above-described determinationprocessing. At least one of steps S1304 to S1306 may be executed.

Although, in the first exemplary embodiment, the document managementapplication 0300 updates the file list upon reception of an event, anunexpected event may occur because of the difference between the OS ofthe file server 0103 and the OS of the information processing apparatus0101. For example, when overwriting an arbitrary file in the monitoringtarget folder is instructed, the situation indicates that an arbitraryfile is changed. Therefore, although the document management application0300 expects the reception of the OnChanged event, it may receive theOnDeleted event and the OnCreated event in succession because of thedifference between the two OS's. The difference between the OS of thefile server 0103 and the OS of the information processing apparatus 0101is, for example, the difference between the OS versions.

A fourth exemplary embodiment will describe a method in which, even if adifferent event occurs for each OS, an updated file is updated at thesame position. In the descriptions of the fourth exemplary embodiment,points duplicated with the first to the third exemplary embodiments willbe omitted.

FIG. 14 is a flowchart illustrating processing for updating the filelist according to a received event.

In the descriptions of FIG. 14, elements duplicated with those in FIG. 6will be omitted. When an event is received (YES in step S0604), then instep S1401, the document management application 0300 performs event waitprocessing. The document management application 0300 changes thereceived event as required through the event wait processing, andperforms steps S0605, S0606, S0607, and S0608 based on the changedevent.

FIG. 15 is a detailed flowchart illustrating the event wait processingin step S1401.

When the received event is the OnDeleted event, the event receiving unit0307 waits for a predetermined time period to receive a new event. Then,when the event receiving unit 0307 receives the OnRenamed event for thesame file name within a predetermined time period, the event receivingunit 0307 changes the OnDeleted event and the OnRenamed event to theOnChanged event. When the event receiving unit 0307 does not receivesthe next event or receives only an event for a different file within apredetermined time period, the event receiving unit 0307 notifies thefile list updating unit 0305 of the received event as it is. As aresult, the document management application 0300 performs processingcorresponding to the relevant event.

In step S1501, the event receiving unit 0307 receives an event. In stepS1502, the event receiving unit 0307 determines whether the receivedevent is the OnDeleted event.

When the received event is determined not to be the OnDeleted event (NOin step S1502), then in step S1506, the event receiving unit 0307notifies the file list updating unit 0305 of the received event as itis.

Otherwise, when the received event is determined to be the OnDeletedevent (YES in step S1502), then in step S1503, the event receiving unit0307 waits for an arbitrary predetermined time period, withoutimmediately notifying the file list updating unit 0305 of the relevantevent.

In step S1504, the event receiving unit 0307 determines whether anotherevent has occurred during the waiting period. When another event has notoccurred (NO in step S1504), then in step S1505, the event receivingunit 0307 determines whether the predetermined time period has elapsed.

When the predetermined time period has elapsed (YES in step S1505), thenin step S1506, the event receiving unit 0307 notifies the file listupdating unit 0305 of the OnDeleted event as it is.

Otherwise, when the event receiving unit 0307 receives another eventduring the waiting period (YES in step S1504), then in step S1507, theevent receiving unit 0307 determines the type of the received event.

When the received event is determined to be the OnCreated event(OnCreated in step S1507), then in step S1509, the event receiving unit0307 deletes the OnDeleted event and the OnCreated event, and changesthe event to the OnChanged event.

When the event which has occurred is determined to be the OnRenamedevent (OnRenamed in step S1507), then in step S1508, the event receivingunit 0307 determines whether the file name of the new file described inthe OnRenamed event is the same as that described in the OnDeletedevent.

When the file name of the new file described in the OnRenamed event isdetermined to be the same as that described in the OnDeleted event (YESin step S1508), then in step S1509, the event receiving unit 0307deletes the OnDeleted event and the OnRenamed event, and changes theevent to the OnChanged event.

Thus, even if an unexpected event occurs because of the differencebetween the OS of the file server 0103 and the OS of the informationprocessing apparatus 0101, the document management application 0300 isable to perform an overwriting operation as expected at the time ofoverwriting. Specifically, the position of an overwritten file remainsunchanged in the file list view 0505.

Even when the event receiving unit 0307 receives the OnDeleted eventfrom the file server 0103, the document management application 0300 isable to suitably determine whether the file corresponding to theOnDeleted event is to be displayed or hidden, by performing theprocessing according to the present exemplary embodiment.

Although, in the above-described first to fourth exemplary embodiments,the file list is updated upon reception of an event, an example ofappending a new file to the end is described. However, when a lot offiles are stored in the monitoring target folder, they cannot bedisplayed in the file list view 0505 without scrolling. In this case,the user may not notice the new file even if it is appended to the end.A fifth exemplary embodiment describes a method for preventing the userfrom overlooking a new file. In the descriptions of the fifth exemplaryembodiment, points duplicated with the first to the fourth exemplaryembodiments will be omitted.

FIG. 16 illustrates an example of a UI for the file list view 0505 ofthe document management application 0300. In the descriptions of FIG.16, elements duplicated with those in FIG. 5 will be omitted. A scrollbar 1601 is displayed when a file list does not fit into the displayarea of the file list view 0505. Vertically moving the scroll bar 1601enables displaying all of files stored in the folder.

When a new file is appended in a state where files A.pdf to G.pdf aredisplayed, as illustrated in the UI in FIG. 16, the new file is insertedat the end of the display area. Then, the example of a UI illustrated inFIG. 16 is changed to an example of a UI illustrated in FIG. 17. When afile H.pdf is appended as a new file, a file 1701 is appended to the endof the display area of the file list view 0505, and the file G.pdf ismoved toward the end.

Thus, appending the new file to the end of the currently viewable areaimproves a search ability when appending a file. In addition, thedocument management application 0300 may simply append a new file to theend, and, at the same time, automatically moves the scroll bar 1601 sothat the new file appended to the end may be displayed.

Moreover, as illustrated in FIG. 20 according to the presentspecification, when a part of existing files 2001 and 2002 in the secondhalf of the file list is displayed in the file list view 0505, a newfile may be appended at the position 1801 illustrated in FIG. 20 inconsideration of user's view.

Embodiments of the present invention can also be realized by a computerof a system or apparatus that reads out and executes computer executableinstructions recorded on a storage medium (e.g., non-transitorycomputer-readable storage medium) to perform the functions of one ormore of the above-described embodiment(s) of the present invention, andby a method performed by the computer of the system or apparatus by, forexample, reading out and executing the computer executable instructionsfrom the storage medium to perform the functions of one or more of theabove-described embodiment(s). The computer may comprise one or more ofa central processing unit (CPU), micro processing unit (MPU), or othercircuitry, and may include a network of separate computers or separatecomputer processors. The computer executable instructions may beprovided to the computer, for example, from a network or the storagemedium. The storage medium may include, for example, one or more of ahard disk, a random-access memory (RAM), a read only memory (ROM), astorage of distributed computing systems, an optical disk (such as acompact disc (CD), digital versatile disc (DVD), or Blu-ray Disc (BD)™),a flash memory device, a memory card, and the like.

According to embodiments of the present invention, the user is able toeasily recognize a change in the monitoring target folder.

While the present invention has been described with reference toexemplary embodiments, it is to be understood that the invention is notlimited to the disclosed exemplary embodiments. The scope of thefollowing claims is to be accorded the broadest interpretation so as toencompass all such modifications and equivalent structures and function.

This application claims the benefit of Japanese Patent Application No.2012-250181 filed Nov. 14, 2012, which is hereby incorporated byreference herein in its entirety.

What is claimed is:
 1. An information processing apparatus connectableto an external apparatus, the information processing apparatuscomprising: a memory storing instructions; and a processor which iscapable of executing the instructions causing the information processingapparatus to: display, on a screen, files existing in a folder of theexternal apparatus, receive an event indicating a change in the folderfrom the external apparatus, and update display content of the screenaccording to the received event, wherein, in a case where a delete eventindicating that a first file of the existing files in the folder is tobe deleted is received from the external apparatus, the display contentof the screen is not updated, and in a case where another eventcorresponding to the first file is further not received from theexternal apparatus within a predetermined time period after receivingthe delete event, the display content of the screen is updated accordingto the delete event so that the first file is deleted, and wherein, in acase where a delete event indicating that a second file of the existingfiles in the folder is to be deleted is received from the externalapparatus, the display content of the screen is not updated, and in acase where an append event, corresponding to second file information,indicating that a new file is appended is further received from theexternal apparatus within a predetermined time period after receivingthe delete event, the delete event and the append event are regarded asevents of change to the second file by a user operation, and the displaycontent of the screen is updated according to the change, withoutupdating the display content of the screen according to the deleteevent.
 2. The information processing apparatus according to claim 1,wherein the instructions further cause the information processingapparatus to: delete the event when the information indicating a changein the folder is an event indicating that a new file has been appendedto the folder and the new file corresponding to the event has a hiddenattribute.
 3. The information processing apparatus according to claim 1,wherein the instructions further cause the information processingapparatus to: delete the event when the information indicating a changein the folder is an event indicating that a new file has been appendedto the folder and an extension of the new file corresponding to theevent is a specific extension.
 4. The information processing apparatusaccording to claim 1, wherein the instructions further cause theinformation processing apparatus to: delete the event when theinformation indicating a change in the folder is an event indicatingthat a new file has been appended to the folder and the new filecorresponding to the event includes a specific name.
 5. The informationprocessing apparatus according to claim 1, wherein, when a delete eventindicating that a third file of the existing files in the folder is tobe deleted is received from the external apparatus and a rename eventindicating that a file name of the third file is changed is furtherreceived from the external apparatus within a predetermined time periodafter receiving the delete event, the display content of the screen isupdated according to a change event indicating that the third file ischanged.
 6. The information processing apparatus according to claim 1,wherein, when the event indicating a change in the folder is received,if a file name received in the event does not exist in a list of theexisting files of the folder and further if a file received in the eventactually exists in the folder of the external apparatus, the screen isupdated so that the existing files are arranged in order according to aspecified sorting method and the file received in the event is appendedto a lower end of the existing files in order not according to thespecified sorting method.
 7. The information processing apparatusaccording to claim 6, wherein, when the event indicating a change in thefolder is received, if the file name received in the event exists in thelist of the existing files of the folder and further if the filereceived in the event actually exists in the folder of the externalapparatus, the screen is updated so that the existing files are arrangedin order according to the specified sorting method and the file receivedin the event is updated at a current display position in the list of theexisting files arranged in order according to the specified sortingmethod, and wherein, when the event indicating a change in the folder isreceived, if the file name received in the event exists in the list ofthe existing files of the folder and further if the file received in theevent does not actually exist in the folder of the external apparatus,the screen is updated so that the existing files are arranged in orderaccording to the specified sorting method and the file received in theevent is deleted from the list of the existing files arranged in orderaccording to the specified sorting method.
 8. The information processingapparatus according to claim 1, wherein a display position of the fileappended according to the append event differs from a display positionof the file changed according to the event of change.
 9. A method forcontrolling an information processing apparatus connectable to anexternal apparatus, the method comprising: displaying, on a screen,files existing in a folder of the external apparatus, receiving an eventindicating a change in the folder from the external apparatus, andupdating display content of the screen according to the received event,wherein, in a case where a delete event indicating that a first file ofthe existing files in the folder is to be deleted is received from theexternal apparatus, the display content of the screen is not updated,and in a case where another event corresponding to the first file isfurther not received from the external apparatus within a predeterminedtime period after receiving the delete event, the display content of thescreen is updated according to the delete event so that the first fileis deleted, and wherein, in a case where a delete event indicating thata second file of the existing files in the folder is to be deleted isreceived from the external apparatus, the display content of the screenis not updated, and in a case where an append event, corresponding tosecond file information, indicating that a new file is appended isfurther received from the external apparatus within a predetermined timeperiod after receiving the delete event, the delete event and the appendevent are regarded as events of change to the second file by a useroperation, and the display content of the screen is updated according tothe change, without updating the display content of the screen accordingto the delete event.
 10. The control method according to claim 9,further comprising: deleting the event when the information indicating achange in the folder is an event indicating that a new file has beenappended to the folder and the new file corresponding to the event has ahidden attribute.
 11. The control method according to claim 9, furthercomprising: deleting the event when the information indicating a changein the folder is an event indicating that a new file has been appendedto the folder and an extension of the new file corresponding to theevent is a specific extension.
 12. The control method according to claim9, further comprising: deleting the event when the informationindicating a change in the folder is an event indicating that a new filehas been appended to the folder and the new file corresponding to theevent includes a specific name.
 13. The control method according toclaim 9, wherein, when a delete event indicating that a third file ofthe existing files in the folder is to be deleted is received from theexternal apparatus and a rename event indicating that a file name of thethird file is changed is further received from the external apparatuswithin a predetermined time period after receiving the delete event, thedisplay content of the screen is updated according to a change eventindicating that the third file is changed.
 14. The control methodaccording to claim 9, wherein, when the event indicating a change in thefolder is received, if a file name received in the event does not existin a list of the existing files of the folder and further if a filereceived in the event actually exists in the folder of the externalapparatus, the screen is updated so that the existing files are arrangedin order according to a specified sorting method and the file receivedin the event is appended to a lower end of the existing files in ordernot according to the specified sorting method.
 15. The control methodaccording to claim 14, wherein, when the event indicating a change inthe folder is received, if the file name received in the event exists inthe list of the existing files of the folder and further if the filereceived in the event actually exists in the folder of the externalapparatus, the screen is updated so that the existing files are arrangedin order according to the specified sorting method and the file receivedin the event is updated at a current display position in the list of theexisting files arranged in order according to the specified sortingmethod, and wherein, when the event indicating a change in the folder isreceived, if the file name received in the event exists in the list ofthe existing files of the folder and further if the file received in theevent does not actually exist in the folder of the external apparatus,the screen is updated so that the existing files are arranged in orderaccording to the specified sorting method and the file received in theevent is deleted from the list of the existing files arranged in orderaccording to the specified sorting method.
 16. The method according toclaim 9, wherein a display position of the file appended according tothe append event differs from a display position of the filed changedaccording to the event of change.
 17. A storage medium storing a programto be executed by a computer connectable to an external apparatus, theprogram causing the computer to execute the following processing:displaying, on a screen, files existing in a folder of the externalapparatus, receiving an event indicating a change in the folder from theexternal apparatus, and updating display content of the screen accordingto the received event, wherein, in a case where a delete eventindicating that a first file of the existing files in the folder is tobe deleted is received from the external apparatus, the display contentof the screen is not updated, and in a case where another eventcorresponding to the first file is further not received from theexternal apparatus within a predetermined time period after receivingthe delete event, the display content of the screen is updated accordingto the delete event so that the first file is deleted, and wherein, in acase where a delete event indicating that a second file of the existingfiles in the folder is to be deleted is received from the externalapparatus, the display content of the screen is not updated, and in acase where an append event, corresponding to second file information,indicating that a new file is appended is further received from theexternal apparatus within a predetermined time period after receivingthe delete event, the delete event and the append event are regarded asevents of change to the second file by a user operation, and the displaycontent of the screen is updated according to the change, withoutupdating the display content of the screen according to the deleteevent.
 18. The storage medium according to claim 17, further comprising:deleting the event when the information indicating a change in thefolder is an event indicating that a new file has been appended to thefolder and the new file corresponding to the event has a hiddenattribute.
 19. The storage medium according to claim 17, furthercomprising: deleting the event when the information indicating a changein the folder is an event indicating that a new file has been appendedto the folder and an extension of the new file corresponding to theevent is a specific extension.
 20. The storage medium according to claim17, further comprising: deleting the event when the informationindicating a change in the folder is an event indicating that a new filehas been appended to the folder and the new file corresponding to theevent includes a specific name.
 21. The storage medium according toclaim 17, wherein, when a delete event indicating that a third file ofthe existing files in the folder is to be deleted is received from theexternal apparatus and a rename event indicating that a file name of thethird file is changed is further received from the external apparatuswithin a predetermined time period after receiving the delete event, thedisplay content of the screen is updated according to a change eventindicating that the third file is changed.
 22. The storage mediumaccording to claim 17, wherein, when the event indicating a change inthe folder is received, if a file name received in the event does notexist in a list of the existing files of the folder and further if afile received in the event actually exists in the folder of the externalapparatus, the screen is updated so that the existing files are arrangedin order according to a specified sorting method and the file receivedin the event is appended to a lower end of the existing files in ordernot according to the specified sorting method.
 23. The storage mediumaccording to claim 22, wherein, when the event indicating a change inthe folder is received, if the file name received in the event exists inthe list of the existing files of the folder and further if the filereceived in the event actually exists in the folder of the externalapparatus, the screen is updated so that the existing files are arrangedin order according to the specified sorting method and the file receivedin the event is updated at a current display position in the list of theexisting files arranged in order according to the specified sortingmethod, and wherein, when the event indicating a change in the folder isreceived, if the file name received in the event exists in the list ofthe existing files of the folder and further if the file received in theevent does not actually exist in the folder of the external apparatus,the screen is updated so that the existing files are arranged in orderaccording to the specified sorting method and the file received in theevent is deleted from the list of the existing files arranged in orderaccording to the specified sorting method.
 24. The storage mediumaccording to claim 17, wherein a display position of the file appendedaccording to the append event differs from a display position of thefile changed according to the file changed to the even of change.